bitkeeper revision 1.1159.212.57 (41fb53cc8wKjvhd8TsN4YHhUYPQCdQ)
authoriap10@labyrinth.cl.cam.ac.uk <iap10@labyrinth.cl.cam.ac.uk>
Sat, 29 Jan 2005 09:13:48 +0000 (09:13 +0000)
committeriap10@labyrinth.cl.cam.ac.uk <iap10@labyrinth.cl.cam.ac.uk>
Sat, 29 Jan 2005 09:13:48 +0000 (09:13 +0000)
commitc3c01ecdbbd2e6a3d2556835f72eac7e33f899fd
tree68decf354158a3b902460771bef43577d5f463f3
parent8fc66e7f572ef0dd11f0b6496df3d2bc88be598a
bitkeeper revision 1.1159.212.57 (41fb53cc8wKjvhd8TsN4YHhUYPQCdQ)

Currently xcs is run by xend in xen-unstable by simply making it a child
process.  If you launch xend from an ssh session, the session won't exit
because the xcs still is connected to it's controlling terminal.

xcs should daemonize itself to prevent this from happening.  This patch
does that along with making the domain id => port mapping dynamically
allocated.

Signed-off-by: Anthony Liguori aliguori@us.ibm.com
tools/xcs/xcs.c